This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
(I had created a response yesterday but it seems to have not gotten saved so reposting from memory. If the other appears, pick one...)
First off, there may be another INI setting that is needed to cause the debug window to appear. Being a developer I set many and leave them on unless they become an issue. Perhaps someone from Technical Support can chime in here and help out on the settings to use. (You may be able to set DEBUG_OUTFILE=C:\ForBruce.log in your Client notes.ini and have the debug output saved to it even if the debug window is not opened. No guarantees but worth a try...)
Ok, for cases like yours where you see no busytime traces on the server there are 2 common causes:
1: Your client Location record is set to use Local only mail addressing rather than Local then Server. You can check this on your current location on the Mail tab. You must use Local then Server or else busytime lookups can fail. (That setting makes the low level logic think you are in Island mode and so all busytime lookups are only done locally which usually means 0 busytime data.)
2: You set the DEBUG_SCHED_ALL=1 setting on the wrong server. Most of the time folks set it on a server other than the Home Server as set on the Location doc (such as the Home Server as defined by the users record in the NAB). You do not want to set it on the Home Server as defined on user record in the NAB because the client is not necessarily going to send the request to that server. The client sends all busytime requests to the Home Server as defined on the Servers tab of your Location doc.
There are other causes of lookup problems but the above 2 are the most likely causes given what I've read so far.
For #2, make sure you set the INI on Home Server that the Location points to and that the server is up. If that server is down, the client will try to fail over to a clustermate and that server is where you want to set the INI. If you have > 2 servers clustered you need to either set it on all of them to make sure you see results OR you can simply change your Home Server in the Location record to a server that is up and then set it on that server.
Bruce
IBM
Feedback response number BKAN8LH4AJ created by ~Lex Nontookonynivu on 09/08/2011